home *** CD-ROM | disk | FTP | other *** search
- In article <lwilliam.3.000D5842@sfalib.sfasu.edu>, lwilliam@sfalib.sfasu.edu (Leigh Williams) says:
- >
- >Has anybody made Mosaic work while also using VLMs instead of NETX on
- >Netware? I had a call today from a site in Connecticut and the guy's having a
- >problem with this. I have Mosaic and the Trumpet winsock working fine here,
- >but we're Netware 3.11 and NETX.EXE. I gave him the Trumpet newsreader to
- >test so we can see if the problem is between winsock and the VLMs, or between
- >Mosaic and the VLM. He can make Mosaic work fine if he doesn't load the
- >Novell stuff. Is this a known problem?
- >
- >Thanks,
- >Leigh Williams
- >Stephen F. Austin State University
- >Nacogdoches, TX 75962 409-568-1421
- >
- Got it to work here. However, after the update to vlm_1.1 my machine will
- hang when exiting windows.
- ------------
- Alan Sterger (818) 393-5906 |alan_t_sterger@ccmail.jpl.nasa.gov
- JPL MS 264-538 | 75210.1022@compuserve.com
- Pasadena, CA Loc 264-534G | asterger@kaiwan.com
- Goin' like a bat out of hell down the Information Super Highway
- From vikas@next.distinct.com Fri Apr 8 02:54:27 1994
- Received: from mail2.netcom.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA26158; Fri, 8 Apr 1994 12:55:59 -0400
- Received: from distinct.com by mail2.netcom.com (8.6.4/SMI-4.1/Netcom)
- id JAA07106; Fri, 8 Apr 1994 09:56:48 -0700
- Received: by distinct.com (NX5.67c/NX3.0M)
- id AA09373; Fri, 8 Apr 94 09:54:28 -0700
- From: Vikas Garg <vikas@next.distinct.com>
- Message-Id: <9404081654.AA09373@distinct.com>
- Subject: Re: Curious behaviour from winsock
- To: icode@teleport.com
- Date: Fri, 8 Apr 1994 09:54:27 -0700 (PDT)
- Cc: winsock@sunsite.unc.edu
- In-Reply-To: <icode.1.00175208@teleport.com> from "Mark Clouden" at Apr 8, 94 00:51:37 am
- X-Mailer: ELM [version 2.4 PL23]
- Content-Type: text
- Content-Length: 1963
-
- >
- > I wonder how many have asked this question before, or alternatively, how many
- > will tell me how obvious my problem is?
- >
- > When using non blocking sockets with lingering enabled (l_onoff=1,
- > l_linger!=0), I call closesocket and get WSAEWOULDBLOCK back. Now great, I
- > expected that, but where is my notification message when it does close?? Or
- > actually, when will it close? - because according to my network monitor app
- > the socket is still connected.
- >
- > I have confirmed that it is not my code - although could easily be my
- > reasoning, by using WSATest (a wonderful help).
- >
- > Basically I have switched to abrubt disconnectes unless someone can point out
- > the err of my ways.
- >
- > I have tried this with Distinct TCP/IP and DEC Pathworks 4.1 and Pathworks 5.0
- > beta.
- >
- > Thanks for any help. I dont now how long I have gone without seeing that this
- > was happening.
- >
- >
- >
-
- You are trying to issue a blocking call on a non blocking socket and that
- is why it is failing with the error code WSAEWOULDBLOCK. Unlike the connect()
- call this implies that the socket will not be closed (page 23 of WINSOCK
- specs).
-
- You have two ways of closing the socket cleanly in this scenario
-
- i) Make the socket blocking and then close it, this will ensure that the
- call does not return untill the socket is properly closed.
-
- ii) Turn linger off, leave the socket as non blocking and close it. In
- this case the call will return immediately and the socket will be close
- sometimes in the future.
-
- Hope this helps
-
- Vikas
-
- ==============================================================
- Vikas Garg Phone : (408) 366-8933 Ex: 105
- Distinct Corp. Fax : (408) 366-0153
- 12901 Saratoga Ave., Ste. 4 E-Mail: vikas@distinct.com
- Saratoga, CA 95070
- U.S.A.
- ==============================================================
- From news@bigblue.oit.unc.edu Fri Apr 8 14:42:56 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA16683; Fri, 8 Apr 1994 14:42:56 -0400
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA28185; Fri, 8 Apr 1994 13:25:18 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: Thu, 7 Apr 1994 14:26:56
- From: jcowall@apounix.apo.ford.com (Jeff G. Cowall)
- Message-Id: <jcowall.12.000E7363@apounix.apo.ford.com>
- Organization: Alliance Program Office, Ford Motor Company
- Sender: ses
- References: <tmunro.1.2DA44031@carleton.ca>
- Subject: Re: WT_WSK.EXE and Novell
-
- In article <tmunro.1.2DA44031@carleton.ca> tmunro@carleton.ca (Tim Munro) writes:
- > I'm having trouble keeping WinTrump's news files on my C: drive and NOT
- on >Netware. I know there is a switch at invocation to do this, something like
- >-ignore_nw. Could someone please tell me the correct switch name? Thanks.
-
- -disable_nw
-
- Works for me.
-
- Park and Lock, Not Responsible...
- From news@bigblue.oit.unc.edu Tue Apr 8 03:36:37 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA21648; Fri, 8 Apr 1994 15:12:56 -0400
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA15779; Fri, 8 Apr 1994 13:46:25 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: 8 Apr 1994 03:36:37 GMT
- From: ddavis@osiris.cso.uiuc.edu (Dave Davis)
- Message-Id: <2o2jg5$l4t@vixen.cso.uiuc.edu>
- Organization: University of Illinois at Urbana
- Sender: ses
- References: <jclund.38.2DA327FF@mmm.com>
- Subject: MS TCP/IP Beta Expiration? [was Re: TCP/IP-32 Beta Expired]
-
- jclund@mmm.com (John C. Lund) writes:
-
- >When I started windows today, 4-6-94, I was informed that my newly installed
- >TCP/IP Beta is expired. According to the Docs. It should expire June 14?
- >I checked my system clock and it is correct. Any ideas?
-
- >John Lund
-
- I just installed this program today (impressed so far!). Does the
- 'expiration' lock you completely out of the TCP/IP functionality? Simply a
- courtesy message/reminder? What are the plans for the final release? I hope
- this will be treated in the same way as the wfwtcp that was placed on
- ftp.microsoft.com a few months back. Can anyone from Microsoft provide some
- guidance on this question?
-
- Thanks,
-
- Dave Davis
- ddavis@osiris.cso.uiuc.edu
-
-